Use the information in the following tables to learn about all possible device connectivity alerts in detail that are raised by Fault Management.
31501 | Managed Device Connectivity Loss |
---|---|
Description | Send an alert when XCO loses contact with SLX. |
Preconditions | The device is registered and the connectivity between devices is
verified during periodic device updates. The polling for connectivity occurs when the device health check is enabled. The following command output is an example of
user
configuration:
efa inventory device setting update --ip=10.10.10.1 --health-check-enable Yes --health-check-interval 6m --health-check-heartbeat-miss-threshold 5 The polling service sends the “DeviceConnectivityFailureAlert” notification when there is a loss of contact. |
Requirements |
Alert shows the following data:
The following example shows an alert when XCO contact with SLX
device is lost:
<114>1 2022-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.4.0”] [alert@1916 resource=”/App/Component/Asset/Device?device_ip=10.10.10.1” alertId=”31501” cause=”connectionEstablishmentError” type=”communicationsAlarm” severity=”major”] [alertData@1916 device_ip=”10.10.10.1” failed_adapters=”ssh rest netconf” failure_reason=”Authentication failed” BOMContact has been lost with device “10.10.10.1” |
Health Response |
Response
{ Resource: /App/Component/Asset/Device?device_ip=10.10.10.1 HQI { Color: Red Value: 4 } StatusText: Contact has been lost with device "10.10.10.1". } |
31502 | Managed Device Connectivity Reestablished |
---|---|
Description | Send an alert when the SLX device is reachable. |
Preconditions | The device is registered, and the connectivity is checked during
normal periodic device updates. The polling for connectivity occurs when the device health check is enabled. The
following is a sample example of user
configuration:
efa inventory device setting update --ip=10.10.10.1 --health-check-enable Yes --health-check-interval 6m --health-check-heartbeat-miss-threshold 5 The polling service sends the “DeviceConnectivitySuccessAlert” notification when an SLX device is not reachable. |
Requirements |
Alert shows the following data:
The following example shows an alert when a device is
unreachable:
<118>1 2022-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.4.0”] [alert@1916 resource=”/App/Component/Asset/Device?device_ip=10.10.10.1” alertId=”31502” cause=”connectionEstablished” type=”communicationsAlarm” severity=”info”] [alertData@1916 device_ip=”10.10.10.1” BOMContact has been regained with device “10.10.10.1”. |
Health Response |
Response
{ Resource: /App/Component/Asset/Device?device_ip=10.10.10.1 HQI { Color: Green Value: 0 } StatusText: Contact has bee regained with device "10.10.10.1". } |
31503 | Managed Device Connectivity Device Removed |
---|---|
Description | Send an alert when the SLX device is removed. |
Preconditions | The “DeviceConnectivityDeviceRemovedAlert” notification is sent when a device is removed. |
Requirements |
Alert shows the following data:
The following example shows an alert when a device is
removed:
<118>1 2022-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.4.0”] [alert@1916 resource=”/App/Component/Asset/Device?device_ip=10.10.10.1” alertId=”31503” cause=”configRemoved” type=”communicationsAlarm” severity=”info”] [alertData@1916 device_ip=”10.10.10.1” BOMDevice “10.10.10.1” has been removed. |
Health Response |
Response
{ Resource: /App/Component/Asset/Device?device_ip=10.10.10.1 HQI { Color: Green Value: 0 } StatusText: Device “10.10.10.1” has been removed. } |